Repository navigation
[TS PBT] Project properties and search violations with USVM - #387
Merged
CaelmBleidd merged 11 commits intoOct 13, 2026
Merged
Conversation
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
from
September 17, 2026 20:31
2d9b65a to
0e2dcb1
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
2 times, most recently
from
September 17, 2026 21:05
be966ff to
1beacb7
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/issue-384-property-contract
branch
from
September 19, 2026 09:53
1a46c28 to
b2f7786
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/issue-384-property-contract
branch
from
September 30, 2026 12:41
0ecfda6 to
ee88851
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
2 times, most recently
from
September 30, 2026 16:04
9dfbf85 to
2ac0342
Compare
Base automatically changed from
caelmbleidd/issue-384-property-contract
to
main
September 30, 2026 16:11
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
from
September 30, 2026 16:15
2ac0342 to
6f4f690
Compare
This was referenced Sep 30, 2026
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
2 times, most recently
from
October 13, 2026 21:06
dff981d to
fa3b0fe
Compare
… engine contracts
CaelmBleidd
force-pushed
the
caelmbleidd/issues-351-352-usvm-property-search
branch
from
October 13, 2026 21:09
fa3b0fe to
ed24ca9
Compare
CaelmBleidd
deleted the
caelmbleidd/issues-351-352-usvm-property-search
branch
October 13, 2026 21:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Project declared PBT domains into USVM and search mapped predicates/preconditions for violations. Independent branch against current main; preserves source constructor constraints and catch routing.
Projection now supports bounded symbolic UTF-16 string contents, nested arrays and optional reference/collection domains. Array regions retain their immediate component type through reads and writes. Witnesses use the final solver model with initial input memory, preserving nested and dynamic payloads before predicate mutation. Configured string/collection bounds are checked before allocation and capped by engine capacity. Reachable unsupported paths retain their reasons and any supported sibling witness.
Preconditions execute before the predicate and keep rejection, escaping exception and non-boolean results distinct. Entry-state configuration and precondition completion are isolated from ordinary interpreter dispatch; runtime/SDK constructor guards remain in place.
Validation: 36 focused USVM projection/search tests, 13 FastCheck contract/conformance tests, and FastCheck backend tests passed locally; usvm-ts and usvm-ts-pbt detektMain/detektTest passed. Regression cases cover nested/optional array mutations, string-array input snapshots, lone surrogates, supplementary characters, configured bounds, catches and mixed unsupported paths. Fresh CI on the published head remains the broader gate.
Review focus: source parameter constraints before configuration, component types versus storage descriptors, snapshot/model selection, UTF-16 bounds and explicit incomplete outcomes. Local witness checks do not establish lone-surrogate JSON wire fidelity; that codec is a separate follow-up. Asynchronous properties and unsupported engine paths remain explicitly classified.